Wow, nice! Thanks for the PR @jkloth .

I am going to deploy the changes. Could you confirm that the builder is operative and running?

(and failing as expected :)

Ah, I though this was expected to succeed. In that case I will mark it as UNSTABLE for now

Ah, I though this was expected to succeed. In that case I will mark it as UNSTABLE for now

In general, I would suggest to always start with UNSTABLE, and only mark as STABLE after 1 week of successful builds.

Ah, I though this was expected to succeed. In that case I will mark it as UNSTABLE for now

It would succeed once https://bugs.python.org/issue45354 (submitted at the same time as the buildbot) is resolved. It seems there is a shortage of developers willing/able to handle Windows-only items.

EDIT: By no means do I expect that there should be immediate responses to every item (issue/PR/whatever) that is brought up, just that really the only nosy-list active contributor is Steve Dower and his time is not infinite :)

It seems there is a shortage of developers willing/able to handle Windows-only items.

Indeed. Maybe you can convince @zooba to take a look :)

Also, one of the problems is to get a Windows 11 machine :(

I would try to install it on my main computer and take a look but there is all the TMP shenanigans and I don't want to deal with that right now.

Also, one of the problems is to get a Windows 11 machine :(

That was my point in getting this buildbot up and running prior to the public release of Win11 on Oct 5th